Topic: Resolving the primary domain via Internet DNS or not?

[kevinb]

Hello everyone,

I have a situation were I want to use the SME 7.0 server as my email server but have the domain name registered with a web host that is handling my website.

The server name is "server" and the domain is "domain.name" (fictitious). The internal static address 192.168.1.1 and and external static address of 22.22.22.22.

The web host has DNS A records of "domain.name = 33.33.33.33" and "*.domain.name = 33.33.33.33". So any address that ends with "domain.name" will be assigned 33.33.33.33.

Now, I can add an "A" record of "server.domain.name = 22.22.22.22" and keep the primary domain as resolved locally.

The issue I see happening is when I go outside the network with my laptop "server.domain.name" will resolve to 22.22.22.22 and when I come back into the the internal network the DNS cache may keep this value. Then when I go to "server.domain.name" I'll be coming at it from the outside and have limited connectivity.

Will this be an issue?


Thanks?


Kevin

[JonB]

Kevin,

Why not get a MX record for domain.com pointed at 33.33.33.33.

The problem with using an A record to point at 33.33.33.33 is your email address then becomes name@something.domain.com rather than name@domain.com

You will however have to POP from something.domain.com

Jon

[CharlieBrady]

The issue I see happening is when I go outside the network with my laptop "server.domain.name" will resolve to 22.22.22.22 and when I come back into the the internal network the DNS cache may keep this value. Then when I go to "server.domain.name" I'll be coming at it from the outside and have limited connectivity.

No, you will be "coming at it" from the inside - web server access lists are determined by source address, not by which address you use as the destination.

[kevinb]

JonB,

I have an MX record "domain.com = mail.domain.com" and an A record "mail.domain.com = 22.22.22.22" and this seams to be working. I am getting email.

I am just learning about this DNS stuff and understood that the MX record was only for email traffic and it has to point to an "A" record.

In any case my concern was having a domain name with two address's (server.domain.com = 192.168.1.1 and server.domain.com = 22.22.22.22).

Thanks for the input.


Charlie,

Thanks for building my confidense. I am trying this now and will report back if I have any issues.


Kevin