Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We have a domain we are hosting internally. We then have a Guest Wireless Belkin Router setup to allow traffic off of our network. The Guest_Wireless Router is setup in front of our firewalls, not behind so I think we have a DNS routing issue. The problem is when on the Guest_Wireless Router we cannot access our domain name. Internet works fine, etc. I know it is something to do with the DNS records that isn’t quite setup right.

Internal Network Configuration Example: We have an A record setup for www on the domain name pointing to say 192.168.1.5 When I do an nslookup on it internally it resolves correctly to 192.168.1.5 and back to our domain controller hosting DNS.

External Network Configuration Example: We have the Guest_Wireless Router setup and you can see result from ipconfig when connected to it.

Connection-specific DNS Suffix. : Guest_Wireless

IPv4 Address. . . . . . . . . . . : 192.168.2.46

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.2.1

DHCP Server . . . . . . . . . . . : 192.168.2.1

DNS Servers . . . . . . . . . . . : 192.168.2.1

NetBIOS over Tcpip. . . . . . . . : Enabled

All internet works fine, just can’t resolve this one domain.

Any ideas?

Thanks

share|improve this question
    
I assume that 192.168.2.1 is your "external Wifi router". What does IT have set as its DNS server? And does that that machine have any knowledge of your "internal domain"? –  tink Mar 7 '13 at 22:25
    
Yes, the 192.168.2.1 is the Guest Wifi router. Meant to test things as if they are offsite. DNS address is 8.8.4.4, which is Google's public DNS. It has a static IP. –  Brian Jackson Mar 14 '13 at 22:53
    
Well there's your problem, then. If your internal DNS points at 192.168.1.5 by name of www.blj.example for internal clients, no one on the outside knows about that. And as 192.168.1.5 isn't routable via the great unwashed it wouldn't make sense to try and resolve it. What you'd need to do is to get an external name record, and poke a hole for port 80 in the firewall to forward to the web-server, or, have a hole in the firewall for DNS from the belkin, and point it at your internal DNS server. –  tink Mar 14 '13 at 23:43

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.