AD DNS RSS Back to forum
@sargasa:
This could be a problem if the internal AD domain name is the same as the public domain name (e.g. domain.com, instead of domain.local or domain.internal or something like that). If ORF needs to check the A or MX record of your public domain (for the SPF test for example, when a spoofed email comes in), it will not find it, because it will check the internal one:
http://blog.vamsoft.com/2010/04/08/tales-from-tech-support-part-13-dns-issues-with-own-domain/
@Krisztián Fekete (Vamsoft): Thanks. So, if external and internal domain names are different, using existing DNS is safe ?
@sargasa: Theoretically, yes: there should not be any issues if the internal and public domain names differ.
What are the downsides of using your existing AD DNS servers ?