warn users against using 127.0.0.1 as a resolver

[djmerlyn]

and here is my resolv.conf file:

PHP Code:
domain mydomain.com
search mydomain.com
nameserver ns1 IP address (happens to be this server)
nameserver ns2 IP address

Change it to

nameserver ns1 IP
nameserver ns2 IP

If it still doesn't work you have a deeper issue...

[noimad1]

Change it to



If it still doesn't work you have a deeper issue...

Ok, so I tried the above still no luck....I tried to ping yahoo.com/google.com and it says "ping: unknown host"

So what kind of things can I do to check for "deeper issues"?

I've also determined this is only happening on 1 out of our 4 servers...and another strange thing...if I type "service named restart" the response is:

Stopping named:
root@sa1 [/etc]#                                           [  OK  ] 

Instead of all others that show this:

Stopping named:                                            [  OK  ]
Starting named:                                            [  OK  ]
root@h1 [/etc]# 

However, like I mentioned in my messages log it says named started fine...?

[noimad1]

Ok, so I tried the above still no luck....I tried to ping yahoo.com/google.com and it says "ping: unknown host"

So what kind of things can I do to check for "deeper issues"?

I've also determined this is only happening on 1 out of our 4 servers...and another strange thing...if I type "service named restart" the response is:

Stopping named:
root@sa1 [/etc]#                                           [  OK  ] 

Instead of all others that show this:

Stopping named:                                            [  OK  ]
Starting named:                                            [  OK  ]
root@h1 [/etc]# 

However, like I mentioned in my messages log it says named started fine...?

Nevermind..I am a complete IDIOT...I appologize for being and IDIOT.....IDIOTS shouldn't be allowed to touch servers....

anyways, the problem was that the IP address listed as our server as the nameserver was actually one diget off....didn't even notice it...it was supposed to have a 155 and it was 156....

Thanks anyways!

[djmerlyn]

So what kind of things can I do to check for "deeper issues"?

Self diagnostics

Glad you got it going!

[ezztro]

Hi,

iam using for Primary Resolver 127.0.0.1
Secondary = non-local NS
Teritary Resolver (optional) = non-local NS

When i change the Primary Resolver to a non-local NS, then exim cant route an outgoing Mail.
WHM cant connect to "cPanel/WHM News"

Why ? So im must switched back ti 127.0.0.1

[FWC]

Hi,

iam using for Primary Resolver 127.0.0.1
Secondary = non-local NS
Teritary Resolver (optional) = non-local NS

When i change the Primary Resolver to a non-local NS, then exim cant route an outgoing Mail.
WHM cant connect to "cPanel/WHM News"

Why ? So im must switched back ti 127.0.0.1

Have you tried your main server IP for the primary resolver?

[ezztro]

yes i have

[chirpy]

...and? If the main IP address does not work, and you have named running, then you must have restrictions at the top of your named.conf which you need to relax as mentioned many times in this thread.

If you get errors in exim with the secondary and tertiary name servers, then they obviously are not providing resolver services to you and are pointless having them in your resolv.conf - you should ask your server provider for ones that actually work.

[ezztro]

...and? If the main IP address does not work, .

The main IP is working.