Facebook
Twitter
J
jamesyeeoc
Guest
gucisanyi -
I think the original problem of DNS not propagating can be easily solved by pointing your development workstation (client PC) to use the Plesk box as the DNS server.
Since you have created the domain 'testdomain' on the Plesk box, then it should be able to resolve as long as your workstation is using the Plesk server as it's primary (or only) DNS, that way the lookup will be served by the Plesk box. Propagation of the DNS records is not necessary if you do it this way.
If you are using a Windows based workstation/client PC, then you could also put an entry in your HOSTS file (C:\WINNT\SYSTEM32\DRIVERS\ETC folder)
Add a line:
<ipaddress> testdomain.com
Windows will then associate that IP with the domainname you specify.
I think the original problem of DNS not propagating can be easily solved by pointing your development workstation (client PC) to use the Plesk box as the DNS server.
Since you have created the domain 'testdomain' on the Plesk box, then it should be able to resolve as long as your workstation is using the Plesk server as it's primary (or only) DNS, that way the lookup will be served by the Plesk box. Propagation of the DNS records is not necessary if you do it this way.
If you are using a Windows based workstation/client PC, then you could also put an entry in your HOSTS file (C:\WINNT\SYSTEM32\DRIVERS\ETC folder)
Add a line:
<ipaddress> testdomain.com
Windows will then associate that IP with the domainname you specify.
