Emails will not send

MeridianSol · 24 Jun 2008 at 10:13

Hi

When sending emails to the domain zyxel.co.uk I get delay messages

When I do a NSLookup check on zyxel.co.uk and against zyxel.com I get the following message

Default Server: w2003sbs01.meridian.local
Address: 192.168.16.2:53

> set q=mx
> zyxel.co.uk
Server: w2003sbs01.meridian.local
Address: 192.168.16.2:53

*** w2003sbs01.meridian.local can't find zyxel.co.uk: Server failed

> zyxel.com
Server: w2003sbs01.meridian.local
Address: 192.168.16.2:53

Non-authoritative answer:
zyxel.com MX preference = 10, mail exchanger = mx01.zyxel.com
zyxel.com MX preference = 90, mail exchanger = mail3.zyxel.com

mx01.zyxel.com internet address = 216.237.21.132
mail3.zyxel.com internet address = 66.59.243.66
>

As you can see I can not resolve zyxel.co.uk on our server

Default Server: w2003sbs01.meridian.local
Address: 192.168.16.2:53

> zyxel.co.uk
Server: w2003sbs01.meridian.local
Address: 192.168.16.2:53

Non-authoritative answer:
Name: zyxel.co.uk
Address: 192.168.16.254

> zyxel.com
Server: w2003sbs01.meridian.local
Address: 192.168.16.2:53

Non-authoritative answer:
Name: zyxel.com
Address: 203.160.254.130

>

Zyxel.co.uk seems to be resolving to our router 192.168.16.254, how do I resolve this

Thanks

TheKnat · 24 Jun 2008 at 10:32

The only thing which springs to mind is that your DNS server (w2003sbs01.meridian.local) has got a forwarder set that for some reason doesn't like zyxel.co.uk

Next thing I would try is to find out what your forwarders are currently set to (DNS Manager/Server Properties/Forwarders) and then do the lookup from them to see if you get the same results. Doing that test should allow you to find out if its your server or the external DNS server your looking at which is at fault.

MeridianSol · 24 Jun 2008 at 10:39

Contacted ISP they ran the same test and got correct results
They use same forwarders as us

So I think it must an internal DNS problem but have no idea how to fix it :confused:

TheKnat · 24 Jun 2008 at 10:44

Tried flushing the dns cache on the server ? Can't think why the server would get that IP stuck in it, but it might be worth a go.

ipconfig /flushdns

MeridianSol · 24 Jun 2008 at 10:57

Tried to flush dns but doesn't resolve the issue

Checked host, and lmhost at C:\WINDOWS\SYSTEM32\DRIVERS\etc

If I ping zyxel.co.uk

It still resolves to our router 192.168.16.254

Can't see where it is getting this from :confused:

MeridianSol · 24 Jun 2008 at 10:57

duplicate post

TheKnat · 24 Jun 2008 at 11:00

Stupid question, but did you flush the cache on both the client and server ? Just to make sure its not stuck anywhere.

If you do an nslookup to the forwarders that the DNS server is using directly, what result do you get ?

MeridianSol · 24 Jun 2008 at 11:10

I've run DNS Flush from server and client machine

I have looked on the servers DNS forward lookup but don't see an entry for zyxel.co.uk

Done on both DNS forwarders

Default Server: w2003sbs01.meridian.local
Address: 192.168.16.2

> 195.7.224.143
Server: w2003sbs01.meridian.local
Address: 192.168.16.2

Name: res02.ision.net.uk
Address: 195.7.224.143

> 195.7.224.57
Server: w2003sbs01.meridian.local
Address: 192.168.16.2

Name: res01.ision.net.uk
Address: 195.7.224.57

MeridianSol · 24 Jun 2008 at 16:09

Think I might contact Zyxel to see if its a known issue with the P662 as its strange that zyxel.co.uk is resolving to the local address of the P662

TheKnat · 24 Jun 2008 at 16:12

That could be a possibility, if its contacting your DNS server.

Is there any sort of hostname or domain name you can set on the P662 that might be causing the problem ?