Print

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

[FurryNutz]

Link>Welcome!

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

Internet Service Provider and Modem Configurations

• What ISP Service do you have? Cable or DSL?
• What ISP Modem Mfr. and model # do you have?

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.

[tgfrules]

Any update on this issue ?

[rojosonic]

Same problem here, DIR-868L, HW:A1, FW: 1.09, when i put my local DNS server as primary DNS, i lost access to the internet.

[FurryNutz]

Link>Welcome!

• What region are you located?
• Has a Factory Reset been performed?
• Was a Factory Reset performed before and after any firmware updates then set up from scratch?

>FW Update Process

• Was the router working before any firmware updates?

Internet Service Provider and Modem Configurations

• What ISP Service do you have? Cable or DSL?
• What ISP Modem Mfr. and model # do you have?

Is DNS relay enabled or disabled when you input custom DNS?

Same problem here, DIR-868L, HW:A1, FW: 1.09, when i put my local DNS server as primary DNS, i lost access to the internet.

[tgfrules]

So I revisited the problem and for some reason I found a workaround.

I setup my DC to have a fixed IP (not the DNS server IP) and internet works fine as expected.
Then I added a second IP, this time the DNS server IP (192.168.5.10). Now it seems that the DC is connectable to internet and the clients can find it.
I am not sure why this works now because I am pretty sure I tried something like this before.

[FurryNutz]

It was mentioned to set a static IP address in earlier posts. Possible a configuration was missed before.

Sound like you have verified a work around.

[FurryNutz]

Maybe you can detail a step by step instruction for future users if this seems to be working for you well. Would be nice to have some instruction on this for users to look at.   

[GewGaw]

I would love this to be corrected. As soon as I enter an internal DNS server none of the clients receive DHCP IPs and DNS resolution is  pooched.

Anyone have gotten word if this is being addressed?

[tgfrules]

As requested here is the workaround for the D-LINK DIR-880L Internal DNS bug.
The bug is when you set the Primary DNS to an internal server the network connection on that server stops.

In order to fix this you setup 2 IP adresses on your internal DNS server like this.
Note that I use the range 192.168.5.XXX which is not default. I see no reason why it should not work with the default range.

First log into your routers web interface. Go to Settings > Internet > Advanced Settings

The Primary DNS server IP should be the IP of your internal DNS Server
The Secondary is Googles DNS which secures a fallback DNS if your internal DNS should fail

On the DNS Server the IP settings should be the following

Make sure that the IP address is within the allowed DHCP range
Default gateway is the IP of the D-Link Router

Then click Advanced and add another IP

The added IP MUST be the IP that you chose earlier as primary DNS server on the router

There you go, a workaround for the 880L DNS bug

[PacketTracer]

Hi,

this workaround obviously only works, if your DNS server uses 192.168.5.7 when talking to the Internet. Don't know how Windows selects the IP source address if there are more than one configured for the same interface. Maybe the order addresses are shown in your last sceenshot is crucial - where Windows always selects the address shown in the first place when it initiates a connection. If so, it should be emphasized as a general rule that the address configured as "Primary DNS Server" inside the router configuration has to be in the second place inside the Windows IP configuration shown in your last screenshot.

PT

[FurryNutz]

And how about some set up information for a interna DNS server? I see some people use Raspberry Pi as a DNS solution. What could users use? Any details on how to set up a DNS server what works in conjunction with a D=Link router would be helpful too.

Thank you for this information. Will copy this to a FAQ sticky for users to use in the FAQ section. 

[GewGaw]

This workaround isn't possible with some appliance based devices such as Synology or QNAP NAS's. Can we issue a request for bug fix or feature update for the firmware.

[FurryNutz]

How so?
Please give some details on how its not working for you?

This workaround isn't possible with some appliance based devices such as Synology or QNAP NAS's. Can we issue a request for bug fix or feature update for the firmware.

[GewGaw]

You are unable to assign a second IP to the same interface. This would mean you need to break a bonded interface (if you are lucky enough to have two or more phyiscal ports on the units) to assign individual IPS to each physical port. I did some some hacks to drop the the Linux shell and add an IP but not exactly a doable work around for most.

[FurryNutz]

Possibly that this issue and the design isn't meant for more than one physical port for these model routers, again, these are home class routers with the average home user in mind. Generally most home users have no need for any additional ports, servers or internal DNS servers. Home users just want things to work with little hassle and little configuration. This issue may not be addressed by D-Link and is saved for business class routers. 

You are unable to assign a second IP to the same interface. This would mean you need to break a bonded interface (if you are lucky enough to have two or more phyiscal ports on the units) to assign individual IPS to each physical port. I did some some hacks to drop the the Linux shell and add an IP but not exactly a doable work around for most.