Re: Possible DNS Issue
- From: "DHJK" <DHJK@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 1 Apr 2005 08:47:01 -0800
Yeah, it's definitely not just you. I was actually using the same DNS
servers as you down here in new york. Now I use 4.2.2.1 and 4.2.2.2 and all
the problems went away. I initially changed my DNS servers to another set of
servers whose IP addresss was supplied to me by Verizon. These didn't work
either so I naively assumed that it wasn't Verizon DNS servers...when in fact
it was.
Cheers.
"David Schrag" wrote:
> I AM SO GLAD I SAW THIS POST! Now I know it's not just me ....
>
> I have 6 clients with SBS servers and two of them are experiencing the exact
> problem you describe. Intermittent ability to resolve names, particularly in
> the afternoon, but never a problem pinging by number. One client says this
> has been going on for about a month; the other thinks it's a more recent
> problem.
>
> The common thread linking my two problem boxes and yours: Verizon. One
> client uses Verizon DSL, the other has a Verizon T1 split between voice and
> data. Both are configured with the standard Massachusetts Verizon DNS
> servers as forwarders: 151.203.0.85 and 151.203.0.84.
>
> It's got to be a Verizon issue, but how are we going to troubleshoot this,
> since Verizon won't do any serious troubleshooting with you unless you hook
> a single computer up to their modem?
>
> "DHJK" <DHJK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:A9221CE1-29C2-4551-99D5-D146CE85A7CF@xxxxxxxxxxxxxxxx
> > For the past month starting at around 1:30PM, 75% of the time I'm unable
> > to
> > resolve hostnames. When I get to work I'll run a constant ping to a
> > random
> > website, say www.google.com. After 1:30PM or thereabouts, if i try to go
> > to
> > google using a web browser or ping google from the command prompt I won't
> > be
> > able to connect. I will, however, be able to ping them through the cmd
> > prompt using an IP address.
> >
> > Server: Windows SBS 2003
> > Clients: 10 - Windows XP SP2
> > Verizon DSL
> > Westell 2200 Modem
> > Linksys Router
> > Linksys switches (2)
> > Watchguard Firebox
> >
> > I checked the DNS Event Logs and nothing came up. I created a debug log
> > yesterday and these are representative of the errors I've seen throughout
> > the
> > log.
> >
> > This just started happening a month or so ago and I'm trying to determine
> > what the cause of this is and how do I fix it. Thanks.
> >
> > 17:51:50 7B0 PACKET UDP Snd 192.168.1.101 0108 R Q [8385 A DR NXDOMAIN]
> > (6)sports(4)espn(2)go(3)com(6)build(5)local(0)
> > UDP response info at 007E7450
> > Socket = 384
> > Remote addr 192.168.1.101, port 1026
> > Time Query=2081297, Queued=0, Expire=0
> > Buf length = 0x0500 (1280)
> > Msg length = 0x0071 (113)
> > Message:
> > XID 0x0108
> > Flags 0x8583
> > QR 1 (RESPONSE)
> > OPCODE 0 (QUERY)
> > AA 1
> > TC 0
> > RD 1
> > RA 1
> > Z 0
> > RCODE 3 (NXDOMAIN)
> > QCOUNT 1
> > ACOUNT 0
> > NSCOUNT 1
> > ARCOUNT 0
> > QUESTION SECTION:
> > Offset = 0x000c, RR count = 0
> > Name "(6)sports(4)espn(2)go(3)com(6)build(5)local(0)"
> > QTYPE A (1)
> > QCLASS 1
> > ANSWER SECTION:
> > empty
> > AUTHORITY SECTION:
> > Offset = 0x0031, RR count = 0
> > Name "(6)build(5)local(0)"
> > TYPE SOA (6)
> > CLASS 1
> > TTL 3600
> > DLEN 40
> > DATA
> > PrimaryServer: (5)alpha[C031](6)build(5)local(0)
> > Administrator: (10)hostmaster(0)
> > SerialNo = 567
> > Refresh = 900
> > Retry = 600
> > Expire = 86400
> > MinimumTTL = 3600
> > ADDITIONAL SECTION:
> > Empty
> >
> >
> >
> > 17:52:10 6A8 PACKET UDP Snd 192.168.1.107 87d7 R Q [8281 DR SERVFAIL]
> > (6)n479ad(11)doubleclick(3)net(0)
> > UDP response info at 007E7450
> > Socket = 384
> > Remote addr 192.168.1.107, port 1119
> > Time Query=2081311, Queued=2081311, Expire=2081316
> > Buf length = 0x0500 (1280)
> > Msg length = 0x0028 (40)
> > Message:
> > XID 0x87d7
> > Flags 0x8182
> > QR 1 (RESPONSE)
> > OPCODE 0 (QUERY)
> > AA 0
> > TC 0
> > RD 1
> > RA 1
> > Z 0
> > RCODE 2 (SERVFAIL)
> > QCOUNT 1
> > ACOUNT 0
> > NSCOUNT 0
> > ARCOUNT 0
> > QUESTION SECTION:
> > Offset = 0x000c, RR count = 0
> > Name "(6)n479ad(11)doubleclick(3)net(0)"
> > QTYPE A (1)
> > QCLASS 1
> > ANSWER SECTION:
> > empty
> > AUTHORITY SECTION:
> > empty
> > ADDITIONAL SECTION:
> > empty
> >
>
>
>
.
- References:
- Possible DNS Issue
- From: DHJK
- Re: Possible DNS Issue
- From: David Schrag
- Possible DNS Issue
- Prev by Date: RE: DC will not authenticate
- Next by Date: Re: SBS Server DNS Problem
- Previous by thread: Re: Possible DNS Issue
- Next by thread: RE: Error on opening Public Folders - c103b404 in ExAdmin
- Index(es):
Relevant Pages
|
