Topic: pop3 doesn't work properly since i changed the DNS server

[funkusmunkus]

Hi all,

I just logged in as admin using putty and followed the simple configure this server, just so I could change the DNS server, and now i can't send mail using outlook, I'm not sure what happened there, I can however recieve mail using outlook, it just times out waiting for response from the sending (SMTP) server when i try sending something.
Yes the SME server is the same one that i changed the DNS record on, and everything else works fine, I can send mail using webmail, there are no DNS problems at all, but changing that must have done something that i'm not aware of.

Any ideas ??

cheers

[djhomeless]

It sounds like POP3 is functioning normally if you can receive mail externally.

Where is your SMTP server located? Where are you located when you do these tests (LAN vs Public net). Are you using your ISP's server, or SME?

If it is local, it makes sense that the webmail package can connect to it, since they are both on localhost. However, outside of a DNS change I suppose there is a chance that SMTP is blocked either by your firewall, or your ISP if your external.

What DNS change did you perform?

Geoffrey

[funkusmunkus]

No I'm on the LAN, and the DNS change was, when your going through configure this server, there is a screen called " select master DNS server address " and I got it to point to the local windows Domain server, the SME is the gatewate server, and is the SMTP server, but I can't see how changing the master DNS server address would effect it, specially seeing as I can still send mail using webmail.

I'm stumpted

[cc_skavenger]

Silly question, but have you rebooted the server.  Changing the DNS server normally doesn't make you reboot.  tinydns and dnscache might be a little hosed.  

Just a thought.

[funkusmunkus]

No i didn't reboot, I thought I wouldn't have to because it doesn't ask you to reboot, and I'd have to schedule a downtime becuase the server is doing a few things, so I was hoping it wouldn't have to anyway, but after your post I restarted both tinydns and dnschace, and it seems to be working now.

I didn't think that changing the DNS server would affect it like that, and after making the changes I would have thought it would restart those services anyway.
shows what I know  

cheers for that by the way