Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[tgfrules]

My setup is like the following.
I use the D-link 880L router with 5-10 client devices.
One of these devices is a Windows Server 2012 which I have set up as a DNS server.
What I did on my old D-link DIR-655 router (and was working just fine for many years) was the following
Router IP: 192.168.5.1
DHCP scope: 192.168.5.50 to 192.168.5.200
Primary DNS server: 192.168.5.10 (the IP of my internal DNS server)
Secondary DNS server: 8.8.8.8 (thats the google DNS for backup in case my internal DNS is down)
DNS relay: False

This resulted in the router would broadcast the two DNS servers to all my client thus making my clients use my internal DNS server. Everything was working just fine.

Now I have setup the same settings on the 880L (well the 880L interface is very different from the DIR-655).
The clients are now getting the two DNS servers just fine (and two extra DNS server which I do not know why - anyways that is not the problem).
The problem is when I set the my internal DNS server to a static IP (the 192.168.5.10) the network traffic is "blocked". I can't even ping the router directly (192.168.5.1) let alone anything else.
If set the DNS server to get an IP automatically (enabling DHCP) it works just fine. But I can't really use that since the IP would be wrong and all my other clients can't get hold of it (when they need for internal DNS lookups)

It seems to me that in the 880L there is a bug when you set a IP of device to the same as the specified DNS server. I hope I have stated my problem clearly and looking forward to any feedback.

Thanks!

[PacketTracer]

Hi,

The problem is when I set the my internal DNS server to a static IP (the 192.168.5.10) the network traffic is "blocked". I can't even ping the router directly (192.168.5.1) let alone anything else.

What kind of network traffic is exactly blocked? Any traffic originating from any LAN PC to the router address (.1) or the Internet? Or just the traffic originating from your internal DNS server (.10)?

If only the second case is true, another theory could be that the DIR-880L has an implicit filter allowing only outgoing traffic originating from the "DHCP scope" (.50 - .200). Hence give it a try and extend this range to .10 - .200 this way including your (still statically configured) internal DNS server. DHCP server (and DHCP client) mechanisms still assure that .10 is not deployed a second time when it is already in use (by your internal DNS server).

PT

[tgfrules]

From the 192.168.5.10 server I can't ping the router (192.168.5.1) or stuff like 8.8.8.8. But I can ping other local machines on the network like 192.168.5.11. From the 192.168.5.11 server I can ping the router (192.168.5.1) and 8.8.8.8 just fine.

I did try to extend the DHCP range to include .10. I restarted 192.168.5.10 and no change. Also 192.168.5.11 still works after the extentions.

[FurryNutz]

Link>Welcome!

• What Hardware version is your router? Look at sticker under router.
• Link>What Firmware version is currently loaded? Found on the routers web page under status.
• What region are you located?

If you set back to default settings with 192.168.0.1 on the 880L router, default DHCP pool address of .100 to .200, set a static IP address on this other DHCP server with DNS support to 192.168.0.10, and all other client devices to Dynamic IP addresses, can you ping and connect from this DNS server PC to the router?

Is the DHCP server portion of this PC enabled or disabled? Having 2 DHCP servers on the same network can be problematic, even though this worked on the prior router model. There maybe some differences on newer generation models.

Is this model router being used in a home or business environment?

[tgfrules]

It's the 880L HW version A1, Firmware 1.01, region EU.
There is no ekstra running DHCP server in the network.
The router is being used in a home environment - even though I don't understand what that could influence

I did what you proposed and reverted to the 192.168.0.X range and only had the DNS server on fixed 192.168.0.10 IP. The internet came back and everything seemed fine. Then I changed the Primary DNS setting on the router to 192.168.0.10 and then problem came back. To me this problem is directly related to the Primary DNS setting on the router which seems cannot be the same as an already used IP in the network.

[PacketTracer]

Looks like you really found a bug in the model's present firmware.

Maybe the following is a workaround that meets your demands:

• Add a second IP address from another network to the LAN interface of your internal DNS server, say 192.168.51.10/24.
• Make sure, that your internal DNS server also listens on this additional address.
• Add a LAN host route for this address to your DIR-880L: 192.168.51.10/255.255.255.255 next hop: 192.168.50.10 (unfortunately not all D-Link routers allow to configure LAN routes, but only WAN routes. Hope this is not the case with DIR-880L)
• In your DIR-880L configure DNS servers 192.168.51.10 and 8.8.8.8

PT

[FurryNutz]

Some info I was given, D-Links newer generation routers don't support loopback for security reasons. Older routers did like the DIR-655. I guess having a lookback presented security issues that D-Link had to close thus no longer supporting lookback. It was mentioned that maybe setting up a Virtual Server rule may allow this kind of configuration. My contact will check on this with his DNS server at home tonight and let me know tomorrow.

[tgfrules]

Thanks PacketTracer for your post - It was a good idea.

Add a LAN host route for this address to your DIR-880L: 192.168.51.10/255.255.255.255 next hop: 192.168.50.10 (unfortunately not all D-Link routers allow to configure LAN routes, but only WAN routes. Hope this is not the case with DIR-880L)

It seems that cannot be setup on the 880L

FurryNutz - I can't really accept that this is a "security feature". Surely there must be a way to setup an internal DNS using the router.

[PacketTracer]

Hi,

if you can't configure the LAN route "192.168.51.10/255.255.255.255 next hop: 192.168.50.10" in your DIR-880L, you can configure it on any client of your LAN instead, e.g. with Windows using "route -p add ..." command.

PT

[tgfrules]

if you can't configure the LAN route "192.168.51.10/255.255.255.255 next hop: 192.168.50.10" in your DIR-880L, you can configure it on any client of your LAN instead, e.g. with Windows using "route -p add ..." command.

A good idea that I might need to fall back to. At least something I need to try.
But it will not work on devices such as my iPhone, Sonos and so on.

[PacketTracer]

Perhaps another idea:

In your DIR-880L leave DNS server configuratuon as is: Primary DNS server: 192.168.5.10 and Secondary DNS server: 8.8.8.8. In addition according to page 97 of the manual enable DNS relay function.

As a consequence your LAN clients get your router's IP address 192.168.5.1 for use as their single DNS server, where the router will relay (at least in theory) clients' DNS requests to your internal DNS server and as a second choice to Google's DNS server if your internal DNS server is down. Maybe in DNS relay mode the DIR-880L does not block your internal DNS server.

PT

[tgfrules]

Didn't work either.

We are running out of options here
If this could just be taken as a bug, so I can get a change in the firmware.

It simple does not make any sense that D-Link does not support internal DNS servers.

[FurryNutz]

FYI, D-Link has this under review to see if this is a supported feature or design or not. My contact could not set up a similar DNS external server and make it work so he's forwarded it on to the lab for analysis.

Please be patient.

[tgfrules]

Thank you - looking forward to a solution

[slhmtb]

I have this same issue. Worked fine on the DIR-655. Spent several hours on the phone with Dlink support trying to resolve it. I hope the new firmware has the fix.