Print

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

[T-man]

I changed dlink 6** router to 890L. Everything else remained the same in internal LAN. (Bind 9.X)

I configured 890 to use internal nameserver 192... For some reason other devices in the LAN cannot query internal DNS. (Even ipconfig says they use internal DNS). On local DNS machine all hosts etc are nicely resolved.

I'm figuring out it must be something in 890 which hinders desired functionality ? Firewall ?

Any ideas where to seek solution?

[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?

Maybe due to loopback isn't supported on this model router?
Which actual "6**" model did you have before the 890L? 

[T-man]

Ex router was DIR-855

New one:
DIR-890L   HW:A1   FW:1.09

[FurryNutz]

Ya I'd like to say the the 855 supported loop back. Not sure though as I didn't have one. Yours still works?

[T-man]

Yep, 855 still works. You had some idea for workaround?

[FurryNutz]

I presume when you had the 855 online your configuration worked with it?

[T-man]

Yes it did work. Create subnet with 855 and connect DNS to it you mean?

[FurryNutz]

Yes.

Only thing I can think of is that the 890L doesn't support loop back where the 855 does.

[T-man]

Hmm. All I want to do is to resolve friendly names inside LAN. On the machine where bind is installed it works like a charm. The other machines can't resolve.

[FurryNutz]

One test you can do, put the 855 back online as the main host router. Disable it's WiFi radios, Connect the 890L up as a LAN to LAN wired running in AP mode:
Bridge Mode vs Relay vs Access Point (AP) / Routers vs Dedicated Access Points (AP)

I'll see if I can get some information from D-Link on this.

[T-man]

Problem solved.

I updated FW 1.11 and opened port 53 (UDP /TCP) in bind server. (windows 10) Now private ips are solved without problems.

[FurryNutz]

Glad you got it working. Thank you for posting on how you did it.
Enjoy. 

[kristopher.lehman]

Hi there,

I have the same problem. Can you confirm that this problem will be solved after upgrading my AC3150?

Thank you! 

[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?

Hi there,

I have the same problem. Can you confirm that this problem will be solved after upgrading my AC3150?

Thank you! 

[Hard Harry]

In case you don't want the port to always be open, try disabling DNS relay and see if that makes the difference. Loopback would only matter if there was a local server on the LAN you were trying to access by public IP. Shouldn't play a role with outbound DNS requests.