Nameserver not resolving working domain

Similar Threads:

1.Domain not resolve but resolve with other ISP domain

Dear All,
 

I'm new to Bind and today I face one problem that one domain
plastics4arab.com not resolve with our DNS server but resolve with another
ISP DNS Server.

 

Presently we are using latest bind 9.2.4 DNS server on Redhat Linux Ent 4.

 

# nslookup

> plastics4arab.com

;; connection timed out; no servers could be reached

> server ns1.shaheer.net.sa

Default server: ns1.shaheer.net.sa

Address: 212.64.128.12#53

> plastics4arab.com

Server:         ns1.shaheer.net.sa

Address:        212.64.128.12#53

 

Non-authoritative answer:

Name:   plastics4arab.com

Address: 75.126.81.155

> exit

 

 

When I use Dig Command 

 

 

# dig plastics4arab.com

 

; <<>> DiG 9.2.4 <<>> plastics4arab.com

;; global options:  printcmd

;; connection timed out; no servers could be reached

 

Can any one help us to solve this issue.

Mohammed Nayeem



 

2.Nameservers not resolving - GoDaddy not helping!

3.Internal domain resolving to external domain not owned by us

Due to a merge, we are now migrating our domain - domain.internal to
the second aquired domain -  domain.net.
Due to certain pressure we have no choice but to migrate in that
direction.

The internal domain.net is the same name as an external domain -
domain.net which is not owned by us.

Some of the machines in both trusted domains are resolving the domain
and server.domain.net to this external address.

the previous administrator was very cavalier and shrugged his
shoulders and explained they always sorted it with host files.

Is there a way in DNS to totally block the resolution to this external
domain, as i really dont like the thought of host files.
And how do we remove this external record from our DNS?

cheers

Phil

4.Domain and email domain the same and not working

Hi...

This is going to be a little tricky to explain, but I'm 
having a BIG problem and I'm hoping there is a really easy 
answer.

I have an outside service that hosts our email under our 
business name.  Lets call it, "mybusiness.com".  When I 
set up our 2000 cluster environment, our domain name 
is "mybusiness.com".  

Now, we are using DSL until our T-1 gets installed...so, I 
had all the clients in the begining using the DSL modem as 
the gateway.  The problem I was having was the network 
load was heavy.  SO, I plugged in the DSL modem into a 
multihommed server, and of course changed the gateway to 
the internal address of the server.  They can use the 
internet with no problem....BUT they cannot receive any 
email.  

Going back to the begining of this email, I explained that 
I have a company that hosts our email using, lets 
say "mybusiness.com". My domain is also 
named "mybusiness.com"

when we try to retrieve email, the message reads that it 
cannot locate the server.

I tried adding a MX record to the DNS...I just hope I did 
it right.  But it still cannot retrieve email from the 
outside server.

I will not rename my domain, due to its a cluster 
environment and I went through hell getting it up in the 
first place.  There has to be an answer to this...I am 
sure there are a number of businesses that use an outside 
email hosting company utilizing the same name of thier 
domain.....I am definetly missing something.

Please help!

Thanks
Nancy

5.Authoritative Nameserver stops resolving its own queries

I would appreciate anyone's help in troubleshooting my problem.  I have an
authoritative nameserver (testy.substantis.com) running bind 9.3.0 on
Fedora Core 2.  The bind install was from sources and performed according
to the Trinity OS instructions where a chrooted version runs for both
external and internal clients.  It works perfectly to both internal
network clients and external clients but has suddenly stopped resolving
its own queries including querries for which it is authoritative.  There
have been no configuration changes and no other changes except a

For example, dig from a client like:
dig dumb.com @testy.substantis.com
returns status: NOERROR

BUT
dig yahoo.com on a terminal on the bind server returns
"connection timed out;  no servers could be reached."

There are no unusual errors in /var/log/messages (i.e. ignoring
"out-of-zone data")

6. Caching only nameserver fails to resolve external zones periodically

7. strange behaviour of resolving nameserver

8. DNS resolving problem (was Static route not working for DNS)