Hey, this is an English text. I want you to translate it into the Tunisian dialect. Please follow these steps:
1. Translate step by step and highlight differences between Tunisian dialect and Modern Standard Arabic.
2. Highlight sections you are confident translating into the Tunisian dialect.
Translate this text into the Tunisian dialect, focusing on capturing the essence of the language nuances:

Q: Moving DNS to a new provider; their servers don't respond but they say it's OK? Currently I have a domain and rent a dedicated server for it. It runs a windows port of BIND (installed by/maintained by Plesk) and provides DNS relevant to my domain I'm looking to wind down that dedicated server and have purchased another one (from OVH, as it happens) onto which a lot of my services have moved, but I haven't installed any DNS daemon on the new server. Instead I've created a zone for my domain on OVH's DNS servers via their control panel Their support tell me that the last step I need to execute to switch everything over is to nominate their DNS servers as responsible for my domain, on the config pages of the registrar The reason I haven't done so so far is that I cannot get their DNS servers to answer any queries! If I do this on my OVH server (note: ns108 is the DNS server that they have allocated to my account): c:\> nslookup > server ns108.ovh.net Default Server: ns108.ovh.net Addresses: 2001:41d0:1:1998::1 213.251.128.152 > google.com *** ns108.ovh.net can't find google.com: No response from server > server 213.251.128.152 Default Server: [213.251.128.152] Address: 213.251.128.152 > google.com *** [213.251.128.152] can't find google.com: Query refused As noted their techs say "just switch it over, it'll all work fine", but it doesn't seem like much of a reassurance. If doesn't matter what domain I put into the query; the response is the same. Is there a technical reason why their servers won't start responding until I nominate them as responsible for my domain, with the registrar? i.e. is what the techs telling me true, that I can switch and not worry? I don't really want to bring down every site we operate as a result of no-one being able to look up our main domain any more - that would be bad for business.. edit: Update: I really struggled with inconsistent behaviour of nslookup here - the solutions below advised me to specify the OVH DNS server on the command line - I thought I HAD specified it (in the way I was using nslookup, by issuing a server dns108.ovh.net command after running nslookup) but it never worked out. I've since determined that it does work when specified in interactive mode, if I use the IPv4 IP of the server rather than its name. I can only assume it's because specifying by name in interactive mode causes the lookup of the server to return an IPv6 address (first) and I suspect this is the one being used, as my system isn't configured for IPv6 Working: c:\> nslookup mail.mydomain.com dns108.ovh.net c:\> nslookup mail.mydomain.com 213.251.188.152 c:\> nslookup >server 213.251.188.152 >mail.mydomain.com Not working: c:\> nslookup >server dns108.ovh.net Default Server: dns108.ovh.net Addresses: 2001:41d0:1:4a98::1 213.251.188.152 >mail.mydomain.com c:\>ping 2001:41d0:1:1998::1 Pinging 2001:41d0:1:1998::1 with 32 bytes of data: PING: transmit failed. General failure. Thanks to all who helped me get to the bottom of this.. Apologies for the misdirection earlier,