DNS Problem

[menemoic]

Hi all,

Im new in this forum, currently we have some problem in our internal dns server, if we lookup to domain *.com like google.com or yahoo.com always lookup to pasfark.net

> google.com

Server: *****

Address: 10.0.0.22

Non-authoritative answer:

Name: google.com.co.id

Address: 216.8.179.24

google.com.co.id nameserver = ns1.fastpark.net

google.com.co.id nameserver = ns2.fastpark.net

ns1.fastpark.net internet address = 216.8.179.50

ns2.fastpark.net internet address = 216.8.177.29

Does anyone know how to resolve this problem?

Many thanks in advance

Hwarid

[cluberti]

Is your DNS server configured to use forwarders, or just root hints? If it just uses root hints, what happens if you configure all domains other than internal to use forwarders (and point them at a service like opendns as the forwarding servers)? It's either poisoning (if you're just using hints) or a problem with the upstream servers you're using for forwarding.

[HAL9000]

Hi all,

Im new in this forum, currently we have some problem in our internal dns server, if we lookup to domain *.com like google.com or yahoo.com always lookup to pasfark.net

> google.com

Server: *****

Address: 10.0.0.22

Non-authoritative answer:

Name: google.com.co.id

Address: 216.8.179.24

google.com.co.id nameserver = ns1.fastpark.net

google.com.co.id nameserver = ns2.fastpark.net

ns1.fastpark.net internet address = 216.8.179.50

ns2.fastpark.net internet address = 216.8.177.29

Does anyone know how to resolve this problem?

Many thanks in advance

Hwarid

It seems that every request to google.com goes to google.com.co.id

may need to be google.co.id - in your internal dns server to open http://www.google.co.id/

This is a request from my computer to google.com.co.id

nslookup -q=any google.com.co.id

Non-authoritative answer:

google.com.co.id internet address = 216.8.179.24

google.com.co.id nameserver = ns2.fastpark.net

google.com.co.id nameserver = ns1.fastpark.net

google.com.co.id

primary name server = ns1.fastpark.net

responsible mail addr = HOSTMASTER.fastpark.net

serial = 2010012000

refresh = 10800 (3 hours)

retry = 1800 (30 mins)

expire = 604800 (7 days)

default TTL = 10800 (3 hours)

google.com.co.id text =

"v=spf1"

and this for google.co.id

nslookup -q=any google.co.id

Non-authoritative answer:

google.co.id internet address = 74.125.87.104

google.co.id internet address = 74.125.87.99

google.co.id MX preference = 10, mail exchanger = google.com.s9b2.psmtp.com

google.co.id MX preference = 10, mail exchanger = google.com.s9b1.psmtp.com

google.co.id MX preference = 10, mail exchanger = google.com.s9a2.psmtp.com

google.co.id MX preference = 10, mail exchanger = google.com.s9a1.psmtp.com

google.co.id nameserver = ns3.google.com

google.co.id nameserver = ns4.google.com

google.co.id nameserver = ns2.google.com

google.co.id nameserver = ns1.google.com

google.co.id

primary name server = ns1.google.com

responsible mail addr = dns-admin.google.com

serial = 1436891

refresh = 21600 (6 hours)

retry = 3600 (1 hour)

expire = 1209600 (14 days)

default TTL = 300 (5 mins)

same thing you have for yahoo.com.co.id

should probably delete ".com" in your server configuration that is probably fault.

or perhaps even worse that you have rule for all sites that *.com goes to *.com.co.id

Edited December 24, 2010 by HAL9000

[menemoic]

Hi all,

My DNS internal is used only just for forwarder, and its happens not only for google.com but for other domain using .com.

we are using Microsoft DNS

Regards,

Hwarid

[cluberti]

So, to whom are you forwarding requests? Do you get the same results in nslookup when using those DNS servers via nslookup as well?

[menemoic]

So, to whom are you forwarding requests? Do you get the same results in nslookup when using those DNS servers via nslookup as well?

I'm forward to our dns external, dns external work fine, we can lookup from dns external. I'm suspect in internal dns

[cluberti]

If it works directly at your forwarders, but not at yours, it is time for clearing your server's cache and using the logging tab to get at the root of the issue.