Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've got a problem with TP-Link soho routers. The DNS forwarder of those routers tends to ignore the DNS servers obtained by DHCP and instead tries sending all DNS requests to this strange IP: That IP doesn't respond.

Has anyone else seen that happen?

share|improve this question
Which TP-Link and firmware version? My 1043ND with vanilla firmware uses DNSes of uplink – Lazy Badger Mar 2 '12 at 15:27

That IP address seems to belong to APNIC - - the "Regional Internet Registry that allocates IP and AS numbers in the Asia Pacific region."

The "whois" information in the APNIC web site for that IP address says that it belongs to the "APNIC Debogon project":

I'm posting those "whois" results at the bottom of this post.

What is the Debogon project? The Wikipedia article about "Bogon Filtering" - - says that "a bogon IP address is a bogus IP address, and an informal name for an IP packet on the public Internet that claims to be from an area of the IP address space reserved, but not yet allocated or delegated by the Internet Assigned Numbers Authority (IANA) or a delegated Regional Internet Registry (RIR). The areas of unallocated address space are called the bogon space."

Having said that, I don't know why your TP-LINK router is sending all DNS requests to that IP address. I also have one TP-LINK router and I don't think it's displaying that behavior. When I get to that router, I'll check it.

EDIT: The TP-Link that I mentioned is a wireless router "TL-WR340G" and it's connected to a cable modem. In the router web interface, in the "Network -> WAN" page, I have the "WAN Connection Type" set to "Static IP" and it is set to an IP address of the same network of the Cable Modem. The "Default Gateway" and "Primary DNS" are both set to the IP address of the Cablem Modem. I hope this helps! :-/

 APNIC found the following authoritative answer from:

% [ node-5]
% Whois data copyright terms

inetnum: -
netname:        Debogon-prefix
descr:          APNIC Debogon Project
descr:          APNIC Pty Ltd
country:        AU
admin-c:        AR302-AP
tech-c:         AR302-AP
mnt-by:         APNIC-HM
mnt-routes:     MAINT-AU-APNIC-GM85-AP
mnt-irt:        IRT-APNICRANDNET-AU
status:         ASSIGNED PORTABLE
changed: 20110922
source:         APNIC

role:           APNIC RESEARCH
address:        PO Box 3646
address:        South Brisbane, QLD 4101
address:        Australia
country:        AU
phone:          +61-7-3858-3188
fax-no:         +61-7-3858-3199
remarks:        ++++++++++++++++++
remarks:        + Address blocks listed with this contact
remarks:        + are withheld from general use and are
remarks:        + only routed briefly for passive testing.
remarks:        +
remarks:        + If you are receiving unwanted traffic
remarks:        + it is almost certainly spoofed source
remarks:        + or hijacked address usage.
remarks:        +
remarks:        +
remarks:        +
remarks:        +
remarks:        ++++++++++++++++++
nic-hdl:        AR302-AP
tech-c:         AH256-AP
admin-c:        AH256-AP
mnt-by:         MAINT-APNIC-AP
changed: 20110822
source:         APNIC
share|improve this answer

I work for an ISP and we use many TP-Link routers (740N, 841N, 941N etc.).All of these routers have that bug when the WAN interface is set to DHCP, even with the latest firmware installed.A way to deal with it is to manually enter the DNS servers in both - WAN and DHCP tabs.

share|improve this answer
Staidaffect, thanks a lot for the workaround. I applied it and it works great now ( relatively speaking. It is still a tplink :) ). Also If anybody has just öne DNS server IP they want to use they can enter the same IP in both fields for wan and dhcp. The device does not complain. – user178392 Jun 19 '13 at 11:11
Interestingly, I was having a similar problem with their consumer router sending out its own IP address as the DNS server over DHCP. It then only seemed to forward to the primary DNS address, which sucked when my ISPs primary DNS server went down. The fix was the same, entering the DNS addresses in both tabs. – BigSandwich Nov 24 '14 at 5:44

Your Answer


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

Not the answer you're looking for? Browse other questions tagged or ask your own question.