D-Link Forums

The Graveyard - Products No Longer Supported => Routers / COVR => DIR-850L => Topic started by: Sireone on March 19, 2015, 06:19:28 PM

Title: Primary DNS blocks access
Post by: Sireone on March 19, 2015, 06:19:28 PM

I think I my have found a bug with the DIR-850L.  Whenever I go to Settings, Internet, Advanced Settings then set the Primary DNS Server to my internal Windows 2008 Server, it blocks access to the router & Internet from that server.  All other clients can access the Internet and the server itself.  If I change the IP address of the Windows server, I can browse the internet fine.  I should be able to use my own DNS server for my internal clients.

Title: Re: Primary DNS blocks access
Post by: FurryNutz on March 19, 2015, 06:46:03 PM

Link>Welcome! (http://forums.dlink.com/index.php?topic=48135.0)

• What Hardware version is your router? Look at sticker under the router case.
• Link>What Firmware (http://forums.dlink.com/index.php?topic=47512.0) version is currently loaded? Found on the routers web page under status.
• What region are you located?

Is the Windows Server your primary DHCP and DNS server?
Is DNS relay enabled on the 850L when you set up custom DNS?

Title: Re: Primary DNS blocks access
Post by: Sireone on March 20, 2015, 04:31:40 AM

Hi, This is a DIR-850L HW:B1 FW:2.03.  I'm in the US.  My Windows Server is not running DHCP, just DNS.  I've tried with DNS Relay on or off.  It still blocks access to the Internet and the router as soon as I set the Primary DNS to my server.  Keep in mind that I need to set this to the server for Active Directory.

Title: Re: Primary DNS blocks access
Post by: FurryNutz on March 20, 2015, 07:25:30 AM

One possibility is that this model router may not support loop back. If your attempting to use a DNS server thats connected on the LAN side them I don't think this will work as DNS services on these routers are directed out the WAN port thru NAT. I don't think you can direct DNS from the router back to a DNS server on the LAN side if this is your configuration.

How is the DIR connected on your system? Please draw a diagram of how it's connected tot he ISP modem and include switches and the WIndows Server...

Title: Re: Primary DNS blocks access
Post by: Sireone on March 20, 2015, 08:11:20 AM

Well, I'm not even interested in having the router use my internal DNS server for itself.  I just want the DHCP server to give out my internal DNS server's IP to my clients.  This is needed for Microsoft Active Directory.  I've use the older DLink routers with the older menu and those work perfectly fine.

This is how everything is layed out:

Interet-----Xfinity SB6121 Modem-----DIR-850L
                                                       |
                                                  DLink Switch
                                                       |
                                                ----------------
                                               |               |
                                            Clients      Windows 2008 Server

Title: Re: Primary DNS blocks access
Post by: PacketTracer on March 20, 2015, 01:51:02 PM

Hi,

as Furry said, this model seems to have a problem with such a configuration like yours.

But from the fact, that your server is a DC and as such has to run 24/7 for your clients to work usefully inside your LAN (access LAN resources authenticated via AD user credentials), why not use it as a DHCP server as well?

The following configuration should work:

• In your router switch off DHCP server function and configure the router's prim. and sec. DNS servers to any external fixed addresses, e.g. those of your ISP if fixed and known, or let these DNS server addresses be dynamically assigned by your ISP during Internet connection setup.
• In your server setup a DHCP server according to your needs and use DHCP option 6 to deploy your server's address as DNS server address to the LAN clients.
• In your DNS server you have two options to enable it to resolve names outside its local authoritative zones: You can either use its default configuration to do an iterative search starting with the list of the Internet root name servers (whose addresses are predefined in your server's configuration, check them to be complete and correct, see the current Root Hints File (http://www.internic.net/domain/named.root)), or you enable DNS forwarding, which causes your DNS server to relay client requests for Internet names to one or more other DNS servers whose addresses you have to configure within the DNS forwarding configuration: You can either use your D-Link router's LAN address as a forwarder address (this requires the router's DNS relay function to be enabled) or any other fixed addresses of external DNS servers, e.g. those of your ISP if fixed and known.

PT

Title: Re: Primary DNS blocks access
Post by: FurryNutz on March 20, 2015, 01:52:45 PM

Thanks for the help and information PT.  ;)

Title: Re: Primary DNS blocks access
Post by: Sireone on March 20, 2015, 02:14:29 PM

Thanks PT.  I'm actually using that suggestion, but was more curious as to why it worked with previous DIR routers but not with the new Cloud Routers. 

Title: Re: Primary DNS blocks access
Post by: PacketTracer on March 20, 2015, 02:40:39 PM

Look at this thread (http://forums.dlink.com/index.php?topic=60881.0), same problem with DIR-880L ...

Title: Re: Primary DNS blocks access
Post by: Sireone on March 20, 2015, 04:29:10 PM

This is a bug and should definitely be addressed.  I've not seen this on any other router.

Title: Re: Primary DNS blocks access
Post by: FurryNutz on March 23, 2015, 06:54:41 AM

This may not be a bug as D-Link may not support loop back in there home class routers. I recommend that you phone contact your regional D-Link support office and ask for help and information regarding this. We find that phone contact has better immediate results over using email.
Let us know how it goes please.