Wanted: guide to DNS @ 1and1 using Plesk 7.5.2?

[StephanK]

I am trying, desperately, to get rid off the 1and1 nameservers.. so far, no luck at all. But lets start from the beginning here...

After a very rocky start... 1&1 butchered the domain registration for "myserver.de" and it took them about a week to fix it and get it online. We're currently "evaluating" a 'Root Server I' at 1&1 Germany running Plesk 7.5.2 on Suse 9.1. Plain 1&1 Setup straight "out of the box". Server is now up and running. So far so good.


Ultimate Goal:
=========
What we want to achieve is NOT having to go through 1&1 to register for domains NOR have NS entries @ Denic point to xy.1and1.de.

IOW: we need to get rid off the 1&1 domain control panel and have our server handle everything DNS related on it's own. I am new to Plesk, i am new to 1&1 and their strange ways of doing things.. So, in short, i am lost..

Has this been achieved before, if yes, how?



Here is where i am currently stuck:
=======================

For now, i'd be happy if the blasted thing would actually use its own NS as primary NS instead of using both primary and secondary NS from 1&1.

- 1&1 Domain Control panel does not let me change primary NS to ns.myserver.de. Neccessary NS and A records are present in the Zone. Error message from 1&1 Domain Control Panel: "Missing Subdomain or Subdomain not ready".

- Called 1&1 Support - Answer: "Please create a subdomain ns.myserver.de".

OK, did that. Didn't make any sense to me, but hey, they're the experts, right? Anyway: same Error.

- Called 1&1 Support - Answer: "Reversmap 123.123.123.123 to myserver.de, wait 8 hours, try again".

Done, waited 8 hours. Still the same error.

- Called 1&1 Support - Answer: "Reversmap 123.123.123.123 to ns.myserver.de, wait 8 hours, try again".

Done, waited another 8 hours. Guess what: still the same error.


Now what? 1&1 Support just told me that there are no Plesk experts available at this time a night, i will get a return call tomorrow morning. But i am losing faith in 1&1s techs..

Anybody able to help?

Thanks a bunch in advance... !

[eWebtricity]

I'm in the process now of creating a tutorial/FAQ on different options for configuring DNS with the Root server products.

In my opinion you should go one of two ways. A) use an external domain registrar and their servers/control panel to manage the zone/records B) use an external domain registrar and point the nameservers to your root server to manage the zone/records.

let me know if you need/want more information on either of these two opinions/scenarios

[StephanK]

B) use an external domain registrar and point the nameservers to your root server to manage the zone/records.

let me know if you need/want more information on either of these two opinions/scenarios

Thanks for your quick answer!

B) is the way we want it to go, however, we cant get anywhere.

So far, we're using ns.myserver.de as primary and slv2.1und1.de as secondary ns.

The problem we're facing right now is, when we edit/add a domain in Plesk, the chages are never transfered to slv2.1und1.de.

Bind does send out notifications, slv2.1und1.de is allowed to do the transfers, it just never seems to actually go get them...

We can now move all our .com/.net domins to this box and they're actually working, but -of course- slv2.1und1.de is reported as lame namesever by dnsreports.com. We still cant move any .DE Domains to this box, as DENIC requires both primary and secodary DNS to respond.

Any clue?

[StephanK]

The problem has been identified. Culprit is slv2.1und1.de. It is unable to resolve its own name.

This unfortunately is not something we customers have control over, so i dropped the idea of using slv2.1und1.de and have added a 2nd IP address to the box and am now providing primary and secondary NS on the same box. Not optimal, but working, at least till i get a second Server up that will provide Secondary NS in future.

Thanks for your help and maybe this does help others out there as well. :)

[nos]

i put a dummy proof simple howtoo in this post. at the end.
http://1and1faq.com/forums/viewtopic.php?t=41

[Star]

I have tried all the suggestions presented in this forum as well as on
sw-soft forums concerning setting up nameservers using a 1and1 root
server with the PLESK control panel. My primary domain and the main
domain on the 1and1 box uses godaddy.com as the registrar. Every time
I try to change the nameservers at godaddy.com I get the following error
Unavailable error in field Host name1
Unavailable error in field Host name2
tests using nslookup at http://www.kloth.net indicate the nameservers are
working as best i can tell yet godaddy.com refuses to accept the name
server entries.
eWebtricity, I could sure use that FAQ/Tutorial if you have it finished as
this is beginning to drive me crazy. I don't wish to take up alot of time or
effort on anyone's part, nor do I wish to post back and forth a ton of
questions and answers. I will finish by saying I do have the main domain
in the 1and1 control panel as an external domain without 1and1
nameservers set. I guess what I need is a full set of step by step
instructions assuming nothing, ie, explaining every single step in the
proper order. Please keep in mind I have tried all the suggestions
presented to date in the forums and its just not working with godaddy.com
Thanks for any possible help and if someone has detailed step by step
instructions, they may email them to me at stormz@charter.net

[eWebtricity]

I know you didn't want a huge question and answer session, but after reading your post it sounds to me like GoDaddy.com isn't configured to recognize your 1and1 Root servers as "Name Servers".

This is a specific configuration and is seperate from all the other typical A records, CNAME records, etc ... In other words you have to specifically tell GoDaddy.com or any registrar for that matter specifically what IP address your nameservers have or are. Then you can set your domain to use those name servers, in our case they are 1and1 root servers. Typically they are the registrar's name servers, which are already registered with the registrar of course.

P.S. The tutorial is halfway finished.

[Star]

The setting nameservers problem with a godaddy.com registered domain is solved. Maybe this will help someone in the future. The problem was
solved with the following procedure.

1. Log into the godaddy account.
2. Click Manage Domains.
3. Click the Domain name of the domain that's going to be nameservers.
4. Click + ( to expand menu ) in the Domain Host Summary section of
Domain Details.
5. Click 'Click here to see details or to modify' in Domain Host Summary
6. Enter NS1, NS2 or whatever in the 'Host:' box next to the domain
name.
7. Enter the IP for the name server in the 'IP Address:' block.
8. Click Add New Host to add another nameserver or go to step 10.
9. Repeat steps 6-8 as needed to add an additional nameserver for the
domain.
10. Click 'Save Changes' when done.
11. After receiving email confirming the changes, return to account
manager and click 'Click here to see details or to modify' under
Nameservers Summary in the Domain Details section.
12. Enter your nameservers in the Custom Name Servers boxes.
13. Click Save Changes.

This seems to force godaddy.com to accept your nameservers as valid.
My nameservers began operating within a matter of about 5 hours but I
suppose it could take more or less time for others.

*** BIG thanks to Cory of Godaddy.com Tech Support for his help! ***