Strange DNS Issue

Status
Not open for further replies.
There is the contents below. Dont think it will help tho with the mail issue. Emails are coming in its just sending out its not

nameserver 213.186.33.99
nameserver 94.23.26.204
nameserver 127.0.0.1
search ovh.net
Click to expand...
 
kevster said:
There is the contents below. Dont think it will help tho with the mail issue. Emails are coming in its just sending out its not
Click to expand...

Why don't you think it will help? The resolv.conf file has to be correct or no emails will go out. resolv.conf does not have anything to do with your websites being visible or mail coming in. It has everything to do with outgoing traffic.
 
I cant see anything wrong with it tho. the 1st ip is the main datacenter ip. second one is my ip and 3rd is localhost
 
Take out nameserver 127.0.0.1 You are probably not running a caching nameserver nor should you be. Exim is probably trying to look up the outgoing email addresses on your own server (127.0.0.1) instead of using the other nameservers.
 
What if i changed it around so it goes to my nameserver first then the dc ip. it may be that
 
kevster said:
I cant see anything wrong with it tho. the 1st ip is the main datacenter ip. second one is my ip and 3rd is localhost
Click to expand...

Then that means at least 2 out of the 3 entries are wrong. Take out your ip and localhost.
 
took out the 127.0.0.1 and the search.ovh.net jst now and rebooting server
 
ovh.net is the people who supply the server and i rebooted it so it could refresh everything
 
This is what I recommend:

Code: 
search yourhostname
nameserver 208.67.222.222
nameserver 208.67.220.220

The nameservers are OpenDNS nameservers.

You can test it by:

Code: 
dig google.com

Should give you:

Code: 
; <<>> DiG 9.3.4-P1 <<>> google.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10021
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             280     IN      A       74.125.67.100
google.com.             280     IN      A       209.85.171.100
google.com.             280     IN      A       74.125.45.100

;; Query time: 45 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Thu Mar  5 10:32:37 2009
;; MSG SIZE  rcvd: 76
 
nameserver 208.67.222.222
nameserver 208.67.220.220

those arent my name server ip;s tho
 
There is me doing dig ultimate-webhost.net

; <<>> DiG 9.3.3rc2 <<>> ultimate-webhost.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57981
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;ultimate-webhost.net. IN A

;; ANSWER SECTION:
ultimate-webhost.net. 13651 IN A 94.23.26.204

;; AUTHORITY SECTION:
ultimate-webhost.net. 13651 IN NS ns1.ultimate-webhost.net.
ultimate-webhost.net. 13651 IN NS ns2.ultimate-webhost.net.

;; ADDITIONAL SECTION:
ns1.ultimate-webhost.net. 163780 IN A 94.23.26.204
ns2.ultimate-webhost.net. 163780 IN A 94.23.121.121

;; Query time: 0 msec
;; SERVER: 213.186.33.99#53(213.186.33.99)
;; WHEN: Thu Mar 5 16:38:43 2009
;; MSG SIZE rcvd: 122
Click to expand...
 
kevster said:
nameserver 208.67.222.222
nameserver 208.67.220.220

those arent my name server ip;s tho
Click to expand...

They are NOT supposed to be YOUR nameserver ip's. That is the whole point.

They are supposed to be the nameservers of either your upstream provider or other publicly available nameservers such as OpenDNS.

There is me doing dig ultimate-webhost.net
Click to expand...

I tell you to do "dig google.com" and then you do "dig ultimate-webhost.net"

When you are ready to follow directions let us know.
 
wouldnt dig google.com giv the same results as yours
but here they are

; <<>> DiG 9.3.3rc2 <<>> google.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54531
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;google.com. IN A

;; ANSWER SECTION:
google.com. 300 IN A 74.125.45.100
google.com. 300 IN A 74.125.67.100
google.com. 300 IN A 209.85.171.100

;; AUTHORITY SECTION:
google.com. 97830 IN NS ns4.google.com.
google.com. 97830 IN NS ns1.google.com.
google.com. 97830 IN NS ns2.google.com.
google.com. 97830 IN NS ns3.google.com.

;; ADDITIONAL SECTION:
ns1.google.com. 194582 IN A 216.239.32.10
ns2.google.com. 187571 IN A 216.239.34.10
ns3.google.com. 187571 IN A 216.239.36.10
ns4.google.com. 187571 IN A 216.239.38.10

;; Query time: 16 msec
;; SERVER: 213.186.33.99#53(213.186.33.99)
;; WHEN: Thu Mar 5 16:56:35 2009
;; MSG SIZE rcvd: 212
Click to expand...
 
wouldnt dig google.com giv the same results as yours
Click to expand...

Absolutely not especially if you don't have your resolv.conf file set up correctly.

Your results:
;; SERVER: 213.186.33.99#53(213.186.33.99)
Click to expand...

My results:
;; SERVER: 208.67.222.222#53(208.67.222.222)
Click to expand...

They are different.

But since yours does return ip results for google.com then your resolv.conf file is probably set up correctly now. Your mail queue should clear eventually.
 
THere is still mail adding onto the list. I have checked all accounts every single file. for the past 5 hours and there is no mailer. There was one but its deleted.
 
Status
Not open for further replies.
Back
Top