I clicked the link (and just tried again), and then tried typing the full address preceded by http and https. All came back with the same message peteandlynnekane.com’s server IP address could not be found.. So something in the public DNS search is missing. It's years since I had to set this up for a site so I cannot remember the exact process, but it has something to do with special record types on a server that point to the public IP address of your site.
A brief overview of what I did first time around
1) I bought a domain name from ionos.com primarily to get a batch of personaliased email addresses
2) Further on down the line I wanted to test some of my API services in a realish world situation so I bought a VM from Linode.com and installed everything required
** I don't think I should have done the next step. **
3) I then changed the default ionos nameservers ( I must of read that I needed to do this ) to the linode ones in an effort to point my domain to the linode box ( I think this is what screwed my email and is totally unneccessary )
Today with help from you guys on here I have a better understanding of what I need to do
What I didn't realise was
1) When I bought the domain with the email package it didn't come with an A record because it didn't need one ( I also didn't know what an A record was ).
2) It came with MX records configured because it neded them.
3) I think by my changing the nameservers my email accounts could not receive email but could send.
Ok this is how I have my setup after all todays shenanigans
After todays education I've realised ( and done ) all I need to do is -
Get the public ip of my Linode box and put it in an A record on my ionos.com account.
The domain is found out in the wild and directed to my Linode box
My email now works
Happy days and thanks to you all
"We can't stop here - this is bat country" - Hunter S Thompson - RIP
Yes, it was my ignorance of DNS and other things - did you read my post explaining what I think I did wrong ? I naively thought the domain would be publicly available ( I didn't think that of course there wasn't a web server runnning on it ) - still don't know how I could get at it though - I don't have any DNS setup locally or any entries in host files either.
"We can't stop here - this is bat country" - Hunter S Thompson - RIP
I have about 30 VB Apps that are humming along on a Windows 2008 server using scheduled tasks. They all do a variety of simple to complex tasks from pulling data and merging letters on a monthly basis, posting data on our website, converting data to crystal reports, etc.
It’s now past the time for us to get off of our Windows 2008 server so I’m taking the apps and converting them up from Visual Studio 2012 to Visual Studio 2019. No real hurdles. Everything is converting fairly clean and running great.
Problems begin when I set the apps up on Windows Server 2019. We have a user that is used for processing tasks and has the appropriate rights on the server. If the tasks are setup to run overnight and I leave the server signed on, the tasks process fine. If I sign off of the server the tasks show that they ran and that they completed successfully, but never finish processing. The status shows they completed at the same time the schedule is triggered, and most of the tasks normally should run 15 minutes to an hour.
Nothing in the event log to say it failed, and I have a good bit of error code built into each program that would fire an error if one was triggered.
The task is setup to “Run whether user is logged on or not”, and also “Run with highest privileges”.
Did something change since 2008 regarding scheduled tasks that I should be aware of? Any suggestions / help with this is appreciated. I’ve Googled it, but haven’t had much luck.
I am pretty much strictly an application developer. I developed an application in my development environment and it needs now to go into an intranet production environment. I will provide the specific details below but my experience in the past has been create the deployment package and give it over to the network guys for them to deploy. Now, I find myself in a position where I have to do the actual production deployment. I have read many articles and watch several videos but really still don't have a good understanding of the actual steps in setting up the server, network components, and configuring the application and network to actually do the move of the application from my development network to the production intranet network. The server is a Windows 2012 r2 server. I will be deploying to the server's IIS. A URL for the application must end in a .mil extension which is the external intranet domain. Can anyone provide me with the basic list of steps in order to do the deployment?
I have two accounts at my work - network account and windows account, with network account I don't have admin privileges - but with Windows account I have admin privileges, I usually login using standard network account so that I can access everything that's available in our network but when I need to install something I am entering the Windows Admin account credentials and installing the software - now I have a question, when installing it gives me message its installed successfully and after restarting the machine when I try to open the IIS - it opens us wizard as iSCSI Initiator Properties Wizard, I don't know - what is Target is?, what should I enter in it, just no idea - just not able to understand - any help please, what's happening with my IIS? thanks a lot.
iSCSI has nothing to do with IIS. It appears that the shortcut you are using to open IIS control panel does not lauch the right tool. Recheck everything: whether IIS is installed with its management panel and required components, and what the link you are using to launch it points to.
"Five fruits and vegetables a day? What a joke!
Personally, after the third watermelon, I'm full."
Hi - we were using TFS for our application, but we were doing deployments manually by using xcopy process, literally, publishing the files onto a local machine - then copying and pasting onto the Servers WebApp folder, now we have moved all our code to Git and TFSVC, now I want to make our build process automatic, any help suggestions or help please, I am new in Source Control Management, any help would be appreciated even links, I am also researching and reading about it - thanks in advance.
Basically I am looking for a Continuous Integration solution for Windows, TFSVC and Git (Git is running on TFSVC Server) with these any free tools to implement Continuous Integration? Any help please?
I have read several tutorials how to manipulate (Linux) "hosts" file.
I need to "connect" Raspberry Pi to PC , using bluetooth.
I really do not care which is server or client end of the connection.
I like to test each piece of hardware by doing local loopback first.
I would like to run such local loopback on each end of the connection separately , using separate code application. I do have the basic - socket / bind / read / write working.
I understand that local "loopback" IP is in range 127.0.0.0 to 127.255.255.255.
1. Can I "bind" created socket to name "localhost" to run such local loopback - using 32 bit address?
2. How can I do same using 128 bit address, ip6 protocol ? AKA how to put ip6 "name" into my C++ code ? ::1 has "multiple" names
3. Is doing "remote loopback" feasible?
Ideally - instruct LOCAL hardware to connect via socket to REMOTE hardware running in "remote loopback"? Or in another words - is there REMOTE loopback IP ? Or do I have to have remote software to emulate such loopback?
4. The communication / socket from (local) RPi woudl "connect / bind " to which IP on remote (PC) hardware?
5. Similar - the communication / socket from (local) PC woudl bind to which IP on now remote - RPi hardware?
Item 5 and 6 would be in "simplex" communication - each one way only - at least for now.
I have not found a decent description of ip6 "names" .
For example -what does ip6-allnodes accomplish ?
The loopback address is always 127.0.0.1, as shown in your hosts files.
1. You bind sockets to IP addresses, not names. So use the appropriate system call to find the correct local address for the name you wish to bind.
2. Use the first name in the hosts file. Multiple names just provide aliases for the address.
3. Not sure what you mean. Loopback by definition is local to the hardware on which the code is running.
4. The client should connect to the server's public address. That is to say, when the server sets up a listening socket, the client needs to know the server's listening address. In internet terms that would be the address found by using DNS lookups. In your tests you just need to hardcode the address in the client code.
5. see 4.
6. The other IP6 names are (probably) use for broadcast messages. Check the relevant RFC document for details.
I need to keep this short, but Like you to know you are no being ignored.
I do understand the 127.0.0.1 as loop back IP .
I am still not sure when IP is "internal protocol" and when Internet protocol.
I take it 127.0.0.1 is an "internal " "IP" address - singular.
I have the "conversion from "nost" name to such IP address done.
So far it looks as I have to have TWO sockets -
one as "plain network" (with loopback 127.0.0.1) and the other as an addition of "RF communication " for future full usage of bluetooth.
I have the "network" socket figured out and working on the RF socket.
I assume they have to be "tied together" somehow.
As far as "remote loopback " goes - such "feature is part of RS232 / EIA standard allowing the originator of the connection to set the receiving end to "remote loop back" to pass the data from the RS232 hardware back to sender without sending it to the attached hardware.
That way the actual transmission path is used both ways without need to communicate to remote system.
Perhaps it can be done by controlling the "RF socket" connection itself.
The “server” ( local PC) allocates a “socket” with parameters
s = socket(AF_BLUETOOTH, SOCK_STREAM, BTPROTO_RFCOMM);
and is set ( waits ) to receive connection from “client”.
It is unclear , but logical that “client terminal “ should be specified - perhaps “client (host) bluetooth address – array of six entries should be entered somewhere – as a “remote address”.
I am using term “terminal X address “ to get away from confusing usage of “address” which can be IP (generic network) or bluetooth address.
So far the term “host” is associated with IP name / address and is really not specific to client or server.
The bluetooth address seems to have no relations to IP address.
The “client” (Rpi) software allocates a “socket” with parameters
socket_descriptor_local = socket(AF_BLUETOOTH, SOCK_STREAM, BTPROTO_RFCOMM);
the “client” - (Rpi ) software originates connection to server ( connect to server bluetooth terminal address ) when data is ready to be passed onto “server” . For now I am passing simple message(s) only.
It is also unclear how / where to specify “client terminal”.
Currently I have two bluetooth hardware (USB) of different class connected.
I do not see how "socket" cares about bluetooth class.
I managed to run both software and received expected errors.
Like to know WHO , not why, actually generates the "connection refused" - logically it should came from "connecting to RECEIVING terminal" , but I am not so sure how to identify that.
To accept connections, the following steps are performed by the server side:
1. A socket is created with socket(2).
2. The socket is bound to a local address using bind(2), so that
other sockets may be connect(2)ed to it.
3. A willingness to accept incoming connections and a queue
limit for incoming connections are specified with listen().
4. Connections are accepted with accept(2).
Yes, that is generally my understanding of "how to".
Sure makes using socket clearer then working with "HCI".
It seems that passing the parameters to "socket" call , especially the DOMAIN and PROTOCOL
"bypasses" the "bind" call.
I need to work on that.
But I got the basic doing expected stuff.
How is this for laymen "definitions "? socket is "high level layer" - overall manager of I/O . bind attaches such socket to "local host" (address) - IP network in general , bluetooth address as option of general. connect attaches such socket via "transmission patch " to "remote" hardware / host , again generally to network (using IP address) , bluetoooth as network specific option using bluetooth address.
modified 1-Jan-20 14:45pm.
Last Visit: 31-Dec-99 18:00 Last Update: 14-Aug-22 9:25