DNS nightmare
DNS nightmare
Good afternoon,
1) I’m using D-Link DSL 584-T with RouterTech AR7RD v 2.91.1.
2) DNS Configuration: Use DNS Proxy – ON, Primary / Secondary DNS server address filled
3) WAN Configuration: Use Peer DNS - ON
4) Internal DNS server configured on Windows 2008 R2, users are pointed to this DNS server
5) Nslookup test produces following results:
a. A record resolution:
Default Server: srv-server.firm.local
Address: 192.168.253.249
> www.google.com
Server: srv-server.firm.local
Address: 192.168.253.249
DNS request timed out.
timeout was 2 seconds.
Non-authoritative answer:
Name: www.l.google.com
Address: 74.125.87.105
Aliases: www.google.com
b. MX record resolution:
Default Server: srv-server.firm.local
Address: 192.168.253.249
> set type=mx
> cvut.cz
Server: srv-server.firm.local
Address: 192.168.253.249
DNS request timed out.
timeout was 2 seconds.
*** Request to srv-server.firm.local timed-out
> cvut.cz
Server: srv-server.firm.local
Address: 192.168.253.249
DNS request timed out.
timeout was 2 seconds.
*** srv-server.firm.local can't find cvut.cz: Server failed
> cvut.cz
Server: srv-server.firm.local
Address: 192.168.253.249
DNS request timed out.
timeout was 2 seconds.
Non-authoritative answer:
cvut.cz MX preference = 100, mail exchanger = ns.cvut.cz
cvut.cz MX preference = 10, mail exchanger = mailgw.cvut.cz
6) There is always a delay – users must press F5 several times to get the page…….
7) IMHO – the best option is turn off DNS Proxy. But after turning off DNS proxy, DNS traffic is blocked on dsl modem.
Is it possible turn off DNS Proxy and path thru DNS traffic from LAN to WAN?
Thanks for any idea…..
Diablo08
1) I’m using D-Link DSL 584-T with RouterTech AR7RD v 2.91.1.
2) DNS Configuration: Use DNS Proxy – ON, Primary / Secondary DNS server address filled
3) WAN Configuration: Use Peer DNS - ON
4) Internal DNS server configured on Windows 2008 R2, users are pointed to this DNS server
5) Nslookup test produces following results:
a. A record resolution:
Default Server: srv-server.firm.local
Address: 192.168.253.249
> www.google.com
Server: srv-server.firm.local
Address: 192.168.253.249
DNS request timed out.
timeout was 2 seconds.
Non-authoritative answer:
Name: www.l.google.com
Address: 74.125.87.105
Aliases: www.google.com
b. MX record resolution:
Default Server: srv-server.firm.local
Address: 192.168.253.249
> set type=mx
> cvut.cz
Server: srv-server.firm.local
Address: 192.168.253.249
DNS request timed out.
timeout was 2 seconds.
*** Request to srv-server.firm.local timed-out
> cvut.cz
Server: srv-server.firm.local
Address: 192.168.253.249
DNS request timed out.
timeout was 2 seconds.
*** srv-server.firm.local can't find cvut.cz: Server failed
> cvut.cz
Server: srv-server.firm.local
Address: 192.168.253.249
DNS request timed out.
timeout was 2 seconds.
Non-authoritative answer:
cvut.cz MX preference = 100, mail exchanger = ns.cvut.cz
cvut.cz MX preference = 10, mail exchanger = mailgw.cvut.cz
6) There is always a delay – users must press F5 several times to get the page…….
7) IMHO – the best option is turn off DNS Proxy. But after turning off DNS proxy, DNS traffic is blocked on dsl modem.
Is it possible turn off DNS Proxy and path thru DNS traffic from LAN to WAN?
Thanks for any idea…..
Diablo08
Re: DNS nightmare
I’m investigating more this problem. There is one more device in this network – Linksys WRVS4400n. The problem is caused by this device and/or router with Routertech firmware. Network scheme is in attached file. Linksys router didn’t accept some DNS packets from D-Link, reason is explained in Log on Linksys:
Oct 28 09:59:49 - Reply packet was to small. Ignoring reply from xxx.yyy.zzz.www (IP of D-Link router)
Oct 28 09:59:49 - unexpected server: aaa.bbb.ccc.ddd (IP of Windows 2008R2 server]
Output from network sniffer before and behind the Linksys will be available soon.
Oct 28 09:59:49 - Reply packet was to small. Ignoring reply from xxx.yyy.zzz.www (IP of D-Link router)
Oct 28 09:59:49 - unexpected server: aaa.bbb.ccc.ddd (IP of Windows 2008R2 server]
Output from network sniffer before and behind the Linksys will be available soon.
Re: DNS nightmare
Are the MTU values on the router and server the same?
Kieran
"Indeed!"
Invaluable links: Forum Rules | Networking Guides | FAQ | Site Search | Forum Search <-- Use it or feel my wrath!
No support via PM, please ask your questions in the forum!
"Indeed!"
Invaluable links: Forum Rules | Networking Guides | FAQ | Site Search | Forum Search <-- Use it or feel my wrath!
No support via PM, please ask your questions in the forum!
Re: DNS nightmare
Good afternoon,
1) My network configuration is in attached file
2) Internal DNS server configured on Windows 2008 R2, users are pointed to this DNS server
3) Nslookup tests produces following results:
a. A record resolution:
Default Server: srv-server.firm.local
Address: 192.168.253.249> http://www.google.com
Server: srv-server.firm.local
Address: 192.168.253.249DNS request timed out.
timeout was 2 seconds.
Non-authoritative answer:
Name: http://www.l.google.com
Address: 74.125.87.105
Aliases: http://www.google.com
b. MX record resolution:
Default Server: srv-server.firm.local
Address: 192.168.253.249
> set type=mx
> cvut.cz
Server: srv-server.firm.local
Address: 192.168.253.249
DNS request timed out.
timeout was 2 seconds.
*** Request to srv-server.firm.local timed-out
> cvut.cz
Server: srv-server.firm.local
Address: 192.168.253.249 DNS request timed out.
timeout was 2 seconds.
*** srv-server.firm.local can't find cvut.cz: Server failed
> cvut.cz
Server: srv-server.firm.local
Address: 192.168.253.249
DNS request timed out.
timeout was 2 seconds. Non-authoritative answer:
cvut.cz MX preference = 100, mail exchanger = ns.cvut.cz
cvut.cz MX preference = 10, mail exchanger = mailgw.cvut.cz
4) There is always a delay in DNS resolution, some packets are lost – users must press F5 several times to get the page…….
5) The problem is caused by Linksys router, reason is explained in Log on Linksys:
Oct 28 09:59:49 - Reply packet was to small. Ignoring reply from xxx.yyy.zzz.www (IP of D-Link router)
Oct 28 09:59:49 - unexpected server: aaa.bbb.ccc.ddd (IP of Windows 2008R2 server]
6) When a Linksys router isn't connected in network infrastructure (we try to use Microsoft ISA, Huawei router or direct connection), everything works like a charm.
7) Because D-Link ADSL router act as DNS proxy, problem could be in D-Link (routertech) DNS implementation.
Thanks for any suggestions how to resolve this…..
1) My network configuration is in attached file
2) Internal DNS server configured on Windows 2008 R2, users are pointed to this DNS server
3) Nslookup tests produces following results:
a. A record resolution:
Default Server: srv-server.firm.local
Address: 192.168.253.249> http://www.google.com
Server: srv-server.firm.local
Address: 192.168.253.249DNS request timed out.
timeout was 2 seconds.
Non-authoritative answer:
Name: http://www.l.google.com
Address: 74.125.87.105
Aliases: http://www.google.com
b. MX record resolution:
Default Server: srv-server.firm.local
Address: 192.168.253.249
> set type=mx
> cvut.cz
Server: srv-server.firm.local
Address: 192.168.253.249
DNS request timed out.
timeout was 2 seconds.
*** Request to srv-server.firm.local timed-out
> cvut.cz
Server: srv-server.firm.local
Address: 192.168.253.249 DNS request timed out.
timeout was 2 seconds.
*** srv-server.firm.local can't find cvut.cz: Server failed
> cvut.cz
Server: srv-server.firm.local
Address: 192.168.253.249
DNS request timed out.
timeout was 2 seconds. Non-authoritative answer:
cvut.cz MX preference = 100, mail exchanger = ns.cvut.cz
cvut.cz MX preference = 10, mail exchanger = mailgw.cvut.cz
4) There is always a delay in DNS resolution, some packets are lost – users must press F5 several times to get the page…….
5) The problem is caused by Linksys router, reason is explained in Log on Linksys:
Oct 28 09:59:49 - Reply packet was to small. Ignoring reply from xxx.yyy.zzz.www (IP of D-Link router)
Oct 28 09:59:49 - unexpected server: aaa.bbb.ccc.ddd (IP of Windows 2008R2 server]
6) When a Linksys router isn't connected in network infrastructure (we try to use Microsoft ISA, Huawei router or direct connection), everything works like a charm.
7) Because D-Link ADSL router act as DNS proxy, problem could be in D-Link (routertech) DNS implementation.
Thanks for any suggestions how to resolve this…..
Re: DNS nightmare
With the non-ROHS firmware you can disable the dnsproxy from the router web gui, but even with "usepeerdns" set it will not pass the ISP servers on via dhcp. You will need to manually assign the dns servers to your upstream devices.
Re: DNS nightmare
What is the manual Primary and Secondary DNS server for the xbox360? I have cox high speed internet at home and the desktop with the Modem is in the living room. I want to hook up xbox live in my room with my laptop. The connection was tested and the network adapter and the IP address passed but the DNS keeps failing. Can anyone help me with this problem?
_________________
_________________
Last edited by belainex on Sat Nov 14, 2009 12:13 pm, edited 1 time in total.
- thechief
- RouterTech Team
- Posts: 12067
- Joined: Wed Feb 01, 2006 10:22 pm
- Location: England, the Centre of Africa
- Contact:
Re: DNS nightmare
I know nothing about the xbox - but why would it need DNS servers different from the router?
The Chief: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
No support via PM. Ask all questions on the open forum.
-
- Newbie
- Posts: 5
- Joined: Wed Sep 16, 2009 10:47 am
Re: DNS nightmare
May be that the dhcp client of the xbox is not completely standard and does not "understand" the dns settings the dhcp server of the router is broadcasting. I remember a similar issue with a PS2, some years ago...
If the xbox operating system allows manual setting of dns then you should try as dns the router ip, i.e. the same as the gateway.
If the xbox operating system allows manual setting of dns then you should try as dns the router ip, i.e. the same as the gateway.