Jump to content

Recommended Posts

Posted

We have 4 DCs all have DNS installed, 3 in one site, one in another. The

4th (in the remote site) when i set itself as the DNS it can not resolve

internet hostnames. It will only work if I set up that server to forward

requests to one of the other DCs, then it's fine.

 

I notice in the debug log:

 

20071011 11:20:37 674 PACKET UDP Snd 193.0.14.129 002c Q [0000

NOERROR] (3)www(3)cnn(3)com(0)

 

20071011 11:20:37 674 PACKET UDP Snd 192.112.36.4 002c Q [0000

NOERROR] (3)www(3)cnn(3)com(0)

 

20071011 11:20:41 674 PACKET UDP Snd 127.0.0.1 9862 R Q [8281

DR SERVFAIL] (3)www(3)cnn(3)com(0)

 

20071011 11:21:19 A2C PACKET UDP Rcv 127.0.0.1 b26c Q [0001

D NOERROR] (8)tsclient(3)usd(5)local(0)

 

20071011 11:21:19 A2C PACKET UDP Snd 127.0.0.1 b26c R Q [8385 A

DR NXDOMAIN] (8)tsclient(3)usd(5)local(0)

 

20071011 11:22:35 A2C PACKET UDP Rcv 127.0.0.1 dc6c Q [0001

D NOERROR] (3)www(7)hotmail(3)com(0)

 

 

 

You can see it goes out to the root hints, but never receives anything back.

Is contacting the root hints different network wise than forwarding request

to another dns server? The server in the remote site is hooked up via point

to point t1 between 2 routers. Is there something I need to enable on the

router? dns helper or something? I just don't understand why forwarding the

request works but using root hints doesn't.

 

-John

  • Replies 3
  • Created
  • Last Reply

Popular Days

Posted

Re: DNS Problems

 

The other thing that I don't know if it has any effect on it, the address

scheme for the remote site is not normal. It's 192.168.0.0 /23 so it's

supernetted (255.255.254.0)

 

 

"John W" <whitesj@union.k12.mo.us> wrote in message

news:eL7AGZCDIHA.3716@TK2MSFTNGP03.phx.gbl...

> We have 4 DCs all have DNS installed, 3 in one site, one in another. The

> 4th (in the remote site) when i set itself as the DNS it can not resolve

> internet hostnames. It will only work if I set up that server to forward

> requests to one of the other DCs, then it's fine.

>

> I notice in the debug log:

>

> 20071011 11:20:37 674 PACKET UDP Snd 193.0.14.129 002c Q [0000

> NOERROR] (3)www(3)cnn(3)com(0)

>

> 20071011 11:20:37 674 PACKET UDP Snd 192.112.36.4 002c Q [0000

> NOERROR] (3)www(3)cnn(3)com(0)

>

> 20071011 11:20:41 674 PACKET UDP Snd 127.0.0.1 9862 R Q [8281

> DR SERVFAIL] (3)www(3)cnn(3)com(0)

>

> 20071011 11:21:19 A2C PACKET UDP Rcv 127.0.0.1 b26c Q [0001

> D NOERROR] (8)tsclient(3)usd(5)local(0)

>

> 20071011 11:21:19 A2C PACKET UDP Snd 127.0.0.1 b26c R Q [8385

> A DR NXDOMAIN] (8)tsclient(3)usd(5)local(0)

>

> 20071011 11:22:35 A2C PACKET UDP Rcv 127.0.0.1 dc6c Q [0001

> D NOERROR] (3)www(7)hotmail(3)com(0)

>

>

>

> You can see it goes out to the root hints, but never receives anything

> back. Is contacting the root hints different network wise than forwarding

> request to another dns server? The server in the remote site is hooked up

> via point to point t1 between 2 routers. Is there something I need to

> enable on the router? dns helper or something? I just don't understand

> why forwarding the request works but using root hints doesn't.

>

> -John

>

Posted

Re: DNS Problems

 

Check your event log.

 

I think I remember there being somethign about haveing forwarding enabled or

root-hints - not both. Disable forwarding and see if your problem goes away.

 

TR

Posted

Re: DNS Problems

 

Didn't work. I think it has something to do with what I said, just

wondering if anyone has any input on it.

 

-John

 

"Travis" <Travis@discussions.microsoft.com> wrote in message

news:116247B4-4E51-4A09-882B-25D41AA2FCEB@microsoft.com...

> Check your event log.

>

> I think I remember there being somethign about haveing forwarding enabled

> or

> root-hints - not both. Disable forwarding and see if your problem goes

> away.

>

> TR


×
×
  • Create New...